Using a configured feedback resource for feedback

ABSTRACT

Apparatuses, methods, and systems are disclosed for using a configured feedback resource for feedback. One method includes transmitting, to a device, configuration information on a transmission resource, wherein the configuration information comprises: resource information for a data transmission; a request for feedback; and a configuration message indicating configuration of a feedback resource. The method includes monitoring for feedback from the device on the feedback resource. The method includes transmitting the data transmission after the monitoring for feedback on the feedback resource.

FIELD

The subject matter disclosed herein relates generally to wirelesscommunications and more particularly relates to using a configuredfeedback resource for feedback.

BACKGROUND

The following abbreviations are herewith defined, at least some of whichare referred to within the following description: Third GenerationPartnership Project (“3GPP”), 4^(th) Generation (“4G”), 5^(th)Generation (“5G”), 5G System (“5GS”), Positive-Acknowledgment (“ACK”),Aggregation Level (“AL”), Access and Mobility Management Function(“AMF”), Access Network (“AN”), Access Point (“AP”), AuthenticationServer Function (“AUSF”), Beam Failure Detection (“BFD”), Binary PhaseShift Keying (“BPSK”), Base Station (“BS”), Buffer Status Report(“BSR”), Bandwidth (“BW”), Bandwidth Part (“BWP”), Carrier Aggregation(“CA”), Contention-Based Random Access (“CBRA”), Clear ChannelAssessment (“CCA”), Control Channel Element (“CCE”), Cyclic DelayDiversity (“CDD”), Code Division Multiple Access (“CDMA”), ControlElement (“CE”), Contention-Free Random Access (“CFRA”), Closed-Loop(“CL”), Coordinated Multipoint (“CoMP”), Cyclic Prefix (“CP”), CyclicalRedundancy Check (“CRC”), Channel State Information (“C SI”), ChannelState Information-Reference Signal (“C SI-RS”), CandidateSingle-subframe Resources (“CSRs”), Common Search Space (“CSS”), ControlResource Set (“CORESET”), Device-to-Device (“D2D”), Discrete FourierTransform Spread (“DFTS”), Downlink Control Information (“DCI”),Downlink (“DL”), Demodulation Reference Signal (“DMRS”), Data RadioBearer (“DRB”), Discontinuous Reception (“DRX”), Downlink Pilot TimeSlot (“DwPTS”), Enhanced Clear Channel Assessment (“eCCA”), EPSConnection Management (“ECM”), Enhanced Mobile Broadband (“eMBB”),Evolved Node B (“eNB”), Effective Isotropic Radiated Power (“EIRP”),European Telecommunications Standards Institute (“ETSI”), Evolved PacketCore (“EPC”), Evolved Packet System (“EPS”), Evolved UniversalTerrestrial Access (“E-UTRA”), Evolved Universal Terrestrial AccessNetwork (“E-UTRAN”), Frame Based Equipment (“FBE”), Frequency DivisionDuplex (“FDD”), Frequency Division Multiplexing (“FDM”), FrequencyDivision Multiple Access (“FDMA”), Frequency Division Orthogonal CoverCode (“FD-OCC”), 5G Node B or Next Generation Node B (“gNB”), GroupLeader (“GL”), General Packet Radio Services (“GPRS”), Guard Period(“GP”), Global System for Mobile Communications (“GSM”), Globally UniqueTemporary UE Identifier (“GUTI”), Home AMF (“hAMF”), Hybrid AutomaticRepeat Request (“HARQ”), Home Location Register (“HLR”), Home PLMN(“HPLMN”), Home Subscriber Server (“HSS”), Identity or Identifier(“ID”), Information Element (“IE”), International Mobile EquipmentIdentity (“IMEI”), International Mobile Subscriber Identity (“IMSI”),International Mobile Telecommunications (“IMT”), Internet-of-Things(“IoT”), Intelligent Transportation Systems Application Identifier(“ITS-AID”), Layer 1 (“L1”), Layer 2 (“L2”), Layer 3 (“L3”), LicensedAssisted Access (“LAA”), Load Based Equipment (“LBE”),Listen-Before-Talk (“LBT”), Logical Channel (“LCH”), Logical ChannelPrioritization (“LCP”), Log-Likelihood Ratio (“LLR”), Long TermEvolution (“LTE”), Multiple Access (“MA”), Medium Access Control(“MAC”), Multimedia Broadcast Multicast Services (“MBMS”), MinimumCommunication Range (“MCR”), Modulation Coding Scheme (“MCS”), MasterInformation Block (“MIB”), Multiple Input Multiple Output (“MIMO”),Mobility Management (“MM”), Mobility Management Entity (“MME”), MobileNetwork Operator (“MNO”), massive MTC (“mMTC”), Maximum Power Reduction(“MPR”), Machine Type Communication (“MTC”), Multi User Shared Access(“MUSA”), Non Access Stratum (“NAS”), Narrowband (“NB”),Negative-Acknowledgment (“NACK”) or (“NAK”), Network Entity (“NE”),Network Function (“NF”), Next Generation RAN (“NG-RAN”), Non-OrthogonalMultiple Access (“NOMA”), New Radio (“NR”), Network Repository Function(“NRF”), Network Slice Instance (“NSI”), Network Slice SelectionAssistance Information (“NSSAI”), Network Slice Selection Function(“NSSF”), Network Slice Selection Policy (“NSSP”), Operation andMaintenance System (“OAM”), Orthogonal Frequency Division Multiplexing(“OFDM”), Open-Loop (“OL”), Other System Information (“OSI”), PowerAngular Spectrum (“PAS”), Physical Broadcast Channel (“PBCH”), PowerControl (“PC”), LTE-to-V2X Interface (“PC5”), Primary Cell (“PCell”),Policy Control Function (““PCF”), Physical Cell ID (“PCID”), PhysicalDownlink Control Channel (“PDCCH”), Packet Data Convergence Protocol(“PDCP”), Physical Downlink Shared Channel (“PDSCH”), Pattern DivisionMultiple Access (“PDMA”), Packet Data Unit (“PDU”), Physical Hybrid ARQIndicator Channel (“PHICH”), Power Headroom (“PH”), Power HeadroomReport (“PHR”), Physical Layer (“PHY”), Platoon Leader (“PL”), PublicLand Mobile Network (“PLMN”), Platoon Member (“PM”), Physical RandomAccess Channel (“PRACH”), Physical Resource Block (“PRB”), PrimarySecondary Cell (“PSCell”), Physical Sidelink Control Channel (“PSCCH”),Physical Sidelink Feedback Channel (“PSFCH”), Provider ServiceIdentifier (“PSID”), Physical Uplink Control Channel (“PUCCH”), PhysicalUplink Shared Channel (“PUSCH”), Quasi Co-Located (“QCL”), Quality ofService (“QoS”), Quadrature Phase Shift Keying (“QPSK”), RegistrationArea (“RA”), Radio Access Network (“RAN”), Radio Access Technology(“RAT”), Random Access Procedure (“RACH”), Random Access Response(“RAR”), Resource Element Group (“REG”), Radio Link Control (“RLC”),Radio Link Monitoring (“RLM”), Radio Network Temporary Identifier(“RNTI”), Reference Signal (“RS”), Remaining Minimum System Information(“RMSI”), Radio Resource Control (“RRC”), Radio Resource Management(“RRM”), Resource Spread Multiple Access (“RSMA”), Reference SignalReceived Power (“RSRP”), Round Trip Time (“RTT”), Receive (“RX”), SparseCode Multiple Access (“SCMA”), Scheduling Request (“SR”), SoundingReference Signal (“SRS”), Single Carrier Frequency Division MultipleAccess (“SC-FDMA”), Secondary Cell (“SCell”), Shared Channel (“SCH”),Sidelink Control Information (“SCP”), Sub-carrier Spacing (“SCS”),Service Data Unit (“SDU”), System Information Block (“SIB”),SystemInformationBlockType1(“SIB1”), SystemInformationBlockType2(“SIB2”), Subscriber Identity/Identification Module (“SIM”),Signal-to-Interference-Plus-Noise Ratio (“SINK”), Sidelink (“SL”),Service Level Agreement (“SLA”), Sidelink Slot Format Indicator(“SL-SFI”), Session Management Function (“SMF”), Special Cell(“SpCell”), Single Network Slice Selection Assistance Information(“S-NSSAI”), Shortened TTI (“sTTI”), Semi-Persistent Scheduling (“SPS”),Sidelink RSRP (“S-RSRP”), Synchronization Signal (“SS”), SynchronizationSignal Block (“SSB”), Scheduling UE (“SUE”), Supplementary Uplink(“SUL”), Subscriber Permanent Identifier (“SUPI”), Candidate ResourceSelection Time Window (“T2”), Tracking Area (“TA”), TA Indicator(“TAP”), Transport Block (“TB”), Transport Block Size (“TB S”),Time-Division Duplex (“TDD”), Time Division Multiplex (“TDM”), TimeDivision Orthogonal Cover Code (“TD-OCC”), Transmission Power Control(“TPC”), Transmission Reception Point (“TRP”), Transmission TimeInterval (“TTI”), Time to Live (“TTL”), Transmit (“TX”), Uplink ControlInformation (“UCI”), Unified Data Management Function (“UDM”), UnifiedData Repository (“UDR”), User Entity/Equipment (Mobile Terminal) (“UE”),Universal Integrated Circuit Card (“UICC”), Uplink (“UL”), UniversalMobile Telecommunications System (“UMTS”), User Plane (“UP”), UplinkPilot Time Slot (“UpPTS”), Ultra-reliability and Low-latencyCommunications (“URLLC”), UE Route Selection Policy (“URSP”), LTE RadioInterface (“Uu”), Vehicle-To-Everything (“V2X”), Visiting AMF (“vAMF”),Visiting NSSF (“vNSSF”), Visiting PLMN (“VPLMN”), InterconnectingInterface (“X2”) (“Xn”), and Worldwide Interoperability for MicrowaveAccess (“WiMAX”).

In certain wireless communications networks, sidelink communication maybe used. In such networks, half duplex sidelink communication may beused and some communications may not be properly received because of thehalf duplex sidelink communication.

BRIEF SUMMARY

Methods for using a configured feedback resource for feedback aredisclosed. Apparatuses and systems also perform the functions of themethod. One embodiment of a method includes transmitting, to a device,configuration information on a transmission resource, wherein theconfiguration information comprises: resource information for a datatransmission; a request for feedback; and a configuration messageindicating configuration of a feedback resource. In certain embodiments,the method includes monitoring for feedback from the device on thefeedback resource. In various embodiments, the method includestransmitting the data transmission after the monitoring for feedback onthe feedback resource.

One apparatus for using a configured feedback resource for feedbackincludes a transmitter that transmits, to a device, configurationinformation on a transmission resource, wherein the configurationinformation comprises: resource information for a data transmission; arequest for feedback; and a configuration message indicatingconfiguration of a feedback resource. In some embodiments, the apparatusincludes a processor that monitors for feedback from the device on thefeedback resource. In certain embodiments, the transmitter transmits thedata transmission after the monitoring for feedback on the feedbackresource.

One embodiment of a method for using a configured feedback resource forfeedback includes receiving, at a device, configuration information on areception resource, wherein the configuration information comprises:resource information for a data transmission; a request for feedback;and a configuration message indicating configuration of a feedbackresource. In certain embodiments, the method includes determiningwhether to transmit feedback on the feedback resource. In someembodiments, the method includes, in response to determining to transmitthe feedback on the feedback resource, transmitting the feedback fromthe device on the feedback resource. In various embodiments, the methodincludes receiving the data transmission after the feedback resource.

One apparatus for using a configured feedback resource for feedbackincludes a receiver that receives configuration information on areception resource, wherein the configuration information comprises:resource information for a data transmission; a request for feedback;and a configuration message indicating configuration of a feedbackresource. In certain embodiments, the apparatus includes a processorthat determines whether to transmit feedback on the feedback resource.In some embodiments, the apparatus includes a transmitter that, inresponse to the processor determining to transmit the feedback on thefeedback resource, transmits the feedback from the apparatus on thefeedback resource. In various embodiments, the receiver receives thedata transmission after the feedback resource.

One embodiment of a method for retransmitting data includes receiving,at a device, a data transmission via sidelink transmission. In certainembodiments, the method includes determining whether a half duplexproblem exists with the data transmission. In some embodiments, themethod includes, in response to determining that the half duplex problemexists with the data transmission, retransmitting the data transmission.

One apparatus for retransmitting data includes a receiver that receivesa data transmission via sidelink transmission. In certain embodiments,the apparatus includes a processor that determines whether a half duplexproblem exists with the data transmission. In some embodiments, theapparatus includes a transmitter that, in response to determining thatthe half duplex problem exists with the data transmission, retransmitsthe data transmission.

BRIEF DESCRIPTION OF THE DRAWINGS

A more particular description of the embodiments briefly described abovewill be rendered by reference to specific embodiments that areillustrated in the appended drawings. Understanding that these drawingsdepict only some embodiments and are not therefore to be considered tobe limiting of scope, the embodiments will be described and explainedwith additional specificity and detail through the use of theaccompanying drawings, in which:

FIG. 1 is a schematic block diagram illustrating one embodiment of awireless communication system for using a configured feedback resourcefor feedback;

FIG. 2 is a schematic block diagram illustrating one embodiment of anapparatus that may be used for using a configured feedback resource forfeedback;

FIG. 3 is a schematic block diagram illustrating one embodiment of anapparatus that may be used for using a configured feedback resource forfeedback;

FIG. 4 is a schematic block diagram illustrating one embodiment of asystem including multiple UEs transmitting at the same time anddifferent frequencies;

FIG. 5 is a schematic block diagram illustrating one embodiment of asystem including multiple UEs transmitting at the same time in the samegroup;

FIG. 6 is a schematic block diagram illustrating one embodiment of aframe structure;

FIG. 7 is a schematic block diagram illustrating another embodiment of aframe structure;

FIG. 8 is a schematic block diagram illustrating a further embodiment ofa frame structure;

FIG. 9 is a schematic block diagram illustrating yet another embodimentof a frame structure;

FIG. 10A is a schematic block diagram illustrating an additionalembodiment of a frame structure;

FIG. 10B is a schematic block diagram illustrating another embodiment ofa frame structure;

FIG. 11 is a schematic block diagram illustrating one embodiment ofcommunications corresponding to group transmissions;

FIG. 12 is a flow chart diagram illustrating one embodiment of a methodfor using a configured feedback resource for feedback;

FIG. 13 is a flow chart diagram illustrating another embodiment of amethod for using a configured feedback resource for feedback; and

FIG. 14 is a flow chart diagram illustrating one embodiment of a methodfor retransmitting data.

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art, aspects of theembodiments may be embodied as a system, apparatus, method, or programproduct. Accordingly, embodiments may take the form of an entirelyhardware embodiment, an entirely software embodiment (includingfirmware, resident software, micro-code, etc.) or an embodimentcombining software and hardware aspects that may all generally bereferred to herein as a “circuit,” “module” or “system.” Furthermore,embodiments may take the form of a program product embodied in one ormore computer readable storage devices storing machine readable code,computer readable code, and/or program code, referred hereafter as code.The storage devices may be tangible, non-transitory, and/ornon-transmission. The storage devices may not embody signals. In acertain embodiment, the storage devices only employ signals foraccessing code.

Certain of the functional units described in this specification may belabeled as modules, in order to more particularly emphasize theirimplementation independence. For example, a module may be implemented asa hardware circuit comprising custom very-large-scale integration(“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such aslogic chips, transistors, or other discrete components. A module mayalso be implemented in programmable hardware devices such as fieldprogrammable gate arrays, programmable array logic, programmable logicdevices or the like.

Modules may also be implemented in code and/or software for execution byvarious types of processors. An identified module of code may, forinstance, include one or more physical or logical blocks of executablecode which may, for instance, be organized as an object, procedure, orfunction. Nevertheless, the executables of an identified module need notbe physically located together, but may include disparate instructionsstored in different locations which, when joined logically together,include the module and achieve the stated purpose for the module.

Indeed, a module of code may be a single instruction, or manyinstructions, and may even be distributed over several different codesegments, among different programs, and across several memory devices.Similarly, operational data may be identified and illustrated hereinwithin modules, and may be embodied in any suitable form and organizedwithin any suitable type of data structure. The operational data may becollected as a single data set, or may be distributed over differentlocations including over different computer readable storage devices.Where a module or portions of a module are implemented in software, thesoftware portions are stored on one or more computer readable storagedevices.

Any combination of one or more computer readable medium may be utilized.The computer readable medium may be a computer readable storage medium.The computer readable storage medium may be a storage device storing thecode. The storage device may be, for example, but not limited to, anelectronic, magnetic, optical, electromagnetic, infrared, holographic,micromechanical, or semiconductor system, apparatus, or device, or anysuitable combination of the foregoing.

More specific examples (a non-exhaustive list) of the storage devicewould include the following: an electrical connection having one or morewires, a portable computer diskette, a hard disk, a random access memory(“RAM”), a read-only memory (“ROM”), an erasable programmable read-onlymemory (“EPROM” or Flash memory), a portable compact disc read-onlymemory (“CD-ROM”), an optical storage device, a magnetic storage device,or any suitable combination of the foregoing. In the context of thisdocument, a computer readable storage medium may be any tangible mediumthat can contain, or store a program for use by or in connection with aninstruction execution system, apparatus, or device.

Code for carrying out operations for embodiments may be any number oflines and may be written in any combination of one or more programminglanguages including an object oriented programming language such asPython, Ruby, Java, Smalltalk, C++, or the like, and conventionalprocedural programming languages, such as the “C” programming language,or the like, and/or machine languages such as assembly languages. Thecode may execute entirely on the user's computer, partly on the user'scomputer, as a stand-alone software package, partly on the user'scomputer and partly on a remote computer or entirely on the remotecomputer or server. In the latter scenario, the remote computer may beconnected to the user's computer through any type of network, includinga local area network (“LAN”) or a wide area network (“WAN”), or theconnection may be made to an external computer (for example, through theInternet using an Internet Service Provider).

Reference throughout this specification to “one embodiment,” “anembodiment,” or similar language means that a particular feature,structure, or characteristic described in connection with the embodimentis included in at least one embodiment. Thus, appearances of the phrases“in one embodiment,” “in an embodiment,” and similar language throughoutthis specification may, but do not necessarily, all refer to the sameembodiment, but mean “one or more but not all embodiments” unlessexpressly specified otherwise. The terms “including,” “comprising,”“having,” and variations thereof mean “including but not limited to,”unless expressly specified otherwise. An enumerated listing of itemsdoes not imply that any or all of the items are mutually exclusive,unless expressly specified otherwise. The terms “a,” “an,” and “the”also refer to “one or more” unless expressly specified otherwise.

Furthermore, the described features, structures, or characteristics ofthe embodiments may be combined in any suitable manner. In the followingdescription, numerous specific details are provided, such as examples ofprogramming, software modules, user selections, network transactions,database queries, database structures, hardware modules, hardwarecircuits, hardware chips, etc., to provide a thorough understanding ofembodiments. One skilled in the relevant art will recognize, however,that embodiments may be practiced without one or more of the specificdetails, or with other methods, components, materials, and so forth. Inother instances, well-known structures, materials, or operations are notshown or described in detail to avoid obscuring aspects of anembodiment.

Aspects of the embodiments are described below with reference toschematic flowchart diagrams and/or schematic block diagrams of methods,apparatuses, systems, and program products according to embodiments. Itwill be understood that each block of the schematic flowchart diagramsand/or schematic block diagrams, and combinations of blocks in theschematic flowchart diagrams and/or schematic block diagrams, can beimplemented by code. The code may be provided to a processor of ageneral purpose computer, special purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions, which execute via the processor of the computer orother programmable data processing apparatus, create means forimplementing the functions/acts specified in the schematic flowchartdiagrams and/or schematic block diagrams block or blocks.

The code may also be stored in a storage device that can direct acomputer, other programmable data processing apparatus, or other devicesto function in a particular manner, such that the instructions stored inthe storage device produce an article of manufacture includinginstructions which implement the function/act specified in the schematicflowchart diagrams and/or schematic block diagrams block or blocks.

The code may also be loaded onto a computer, other programmable dataprocessing apparatus, or other devices to cause a series of operationalsteps to be performed on the computer, other programmable apparatus orother devices to produce a computer implemented process such that thecode which execute on the computer or other programmable apparatusprovide processes for implementing the functions/acts specified in theflowchart and/or block diagram block or blocks.

The schematic flowchart diagrams and/or schematic block diagrams in theFigures illustrate the architecture, functionality, and operation ofpossible implementations of apparatuses, systems, methods and programproducts according to various embodiments. In this regard, each block inthe schematic flowchart diagrams and/or schematic block diagrams mayrepresent a module, segment, or portion of code, which includes one ormore executable instructions of the code for implementing the specifiedlogical function(s).

It should also be noted that, in some alternative implementations, thefunctions noted in the block may occur out of the order noted in theFigures. For example, two blocks shown in succession may, in fact, beexecuted substantially concurrently, or the blocks may sometimes beexecuted in the reverse order, depending upon the functionalityinvolved. Other steps and methods may be conceived that are equivalentin function, logic, or effect to one or more blocks, or portionsthereof, of the illustrated Figures.

Although various arrow types and line types may be employed in theflowchart and/or block diagrams, they are understood not to limit thescope of the corresponding embodiments. Indeed, some arrows or otherconnectors may be used to indicate only the logical flow of the depictedembodiment. For instance, an arrow may indicate a waiting or monitoringperiod of unspecified duration between enumerated steps of the depictedembodiment. It will also be noted that each block of the block diagramsand/or flowchart diagrams, and combinations of blocks in the blockdiagrams and/or flowchart diagrams, can be implemented by specialpurpose hardware-based systems that perform the specified functions oracts, or combinations of special purpose hardware and code.

The description of elements in each figure may refer to elements ofproceeding figures. Like numbers refer to like elements in all figures,including alternate embodiments of like elements.

FIG. 1 depicts an embodiment of a wireless communication system 100 forusing a configured feedback resource for feedback. In one embodiment,the wireless communication system 100 includes remote units 102 andnetwork units 104. Even though a specific number of remote units 102 andnetwork units 104 are depicted in FIG. 1, one of skill in the art willrecognize that any number of remote units 102 and network units 104 maybe included in the wireless communication system 100.

In one embodiment, the remote units 102 may include computing devices,such as desktop computers, laptop computers, personal digital assistants(“PDAs”), tablet computers, smart phones, smart televisions (e.g.,televisions connected to the Internet), set-top boxes, game consoles,security systems (including security cameras), vehicle on-boardcomputers, network devices (e.g., routers, switches, modems), aerialvehicles, drones, or the like. In some embodiments, the remote units 102include wearable devices, such as smart watches, fitness bands, opticalhead-mounted displays, or the like. Moreover, the remote units 102 maybe referred to as subscriber units, mobiles, mobile stations, users,terminals, mobile terminals, fixed terminals, subscriber stations, UE,user terminals, a device, or by other terminology used in the art. Theremote units 102 may communicate directly with one or more of thenetwork units 104 via UL communication signals. The remote units 102 mayalso communicate directly with one or more of the other remote units102.

The network units 104 may be distributed over a geographic region. Incertain embodiments, a network unit 104 may also be referred to as anaccess point, an access terminal, a base, a base station, a Node-B, aneNB, a gNB, a Home Node-B, a relay node, a device, a core network, anaerial server, a radio access node, an AP, NR, a network entity, an AMF,a UDM, a UDR, a UDM/UDR, a PCF, a RAN, an NSSF, or by any otherterminology used in the art. The network units 104 are generally part ofa radio access network that includes one or more controllerscommunicably coupled to one or more corresponding network units 104. Theradio access network is generally communicably coupled to one or morecore networks, which may be coupled to other networks, like the Internetand public switched telephone networks, among other networks. These andother elements of radio access and core networks are not illustrated butare well known generally by those having ordinary skill in the art.

In one implementation, the wireless communication system 100 iscompliant with NR protocols standardized in 3GPP, wherein the networkunit 104 transmits using an OFDM modulation scheme on the DL and theremote units 102 transmit on the UL using a SC-FDMA scheme or an OFDMscheme. More generally, however, the wireless communication system 100may implement some other open or proprietary communication protocol, forexample, WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants,CDMA2000, Bluetooth®, ZigBee, Sigfoxx, among other protocols. Thepresent disclosure is not intended to be limited to the implementationof any particular wireless communication system architecture orprotocol.

The network units 104 may serve a number of remote units 102 within aserving area, for example, a cell or a cell sector via a wirelesscommunication link. The network units 104 transmit DL communicationsignals to serve the remote units 102 in the time, frequency, and/orspatial domain.

In one embodiment, a remote unit 102 may transmit, to a device,configuration information on a transmission resource, wherein theconfiguration information comprises: resource information for a datatransmission; a request for feedback; and a configuration messageindicating configuration of a feedback resource. In certain embodiments,the remote unit 102 may monitor for feedback from the device on thefeedback resource. In various embodiments, the remote unit 102 maytransmit the data transmission after the monitoring for feedback on thefeedback resource. Accordingly, the remote unit 102 may be used forusing a configured feedback resource for feedback.

In another embodiment, a remote unit 102 may receive, at a device,configuration information on a reception resource, wherein theconfiguration information comprises: resource information for a datatransmission; a request for feedback; and a configuration messageindicating configuration of a feedback resource. In certain embodiments,the remote unit 102 may determine whether to transmit feedback on thefeedback resource. In some embodiments, the remote unit 102 may, inresponse to determining to transmit the feedback on the feedbackresource, transmit the feedback from the device on the feedbackresource. In various embodiments, the remote unit 102 may receive thedata transmission after the feedback resource. Accordingly, the remoteunit 102 may be used for using a configured feedback resource forfeedback.

In one embodiment, a remote unit 102 may receive, at a device, a datatransmission via sidelink transmission. In certain embodiments, theremote unit 102 may determine whether a half duplex problem exists withthe data transmission. In some embodiments, the remote unit 102 may, inresponse to determining that the half duplex problem exists with thedata transmission, retransmit the data transmission. Accordingly, theremote unit 102 may be used for retransmitting data.

FIG. 2 depicts one embodiment of an apparatus 200 that may be used forusing a configured feedback resource for feedback. The apparatus 200includes one embodiment of the remote unit 102. Furthermore, the remoteunit 102 may include a processor 202, a memory 204, an input device 206,a display 208, a transmitter 210, and a receiver 212. In someembodiments, the input device 206 and the display 208 are combined intoa single device, such as a touchscreen. In certain embodiments, theremote unit 102 may not include any input device 206 and/or display 208.In various embodiments, the remote unit 102 may include one or more ofthe processor 202, the memory 204, the transmitter 210, and the receiver212, and may not include the input device 206 and/or the display 208.

The processor 202, in one embodiment, may include any known controllercapable of executing computer-readable instructions and/or capable ofperforming logical operations. For example, the processor 202 may be amicrocontroller, a microprocessor, a central processing unit (“CPU”), agraphics processing unit (“GPU”), an auxiliary processing unit, a fieldprogrammable gate array (“FPGA”), or similar programmable controller. Insome embodiments, the processor 202 executes instructions stored in thememory 204 to perform the methods and routines described herein. Invarious embodiments, the processor 202 monitors for feedback from thedevice on the feedback resource. In certain embodiments, the processor202 determines whether to transmit feedback on the feedback resource. Insome embodiments, the processor 202 determines whether a half duplexproblem exists with the data transmission. The processor 202 iscommunicatively coupled to the memory 204, the input device 206, thedisplay 208, the transmitter 210, and the receiver 212.

The memory 204, in one embodiment, is a computer readable storagemedium. In some embodiments, the memory 204 includes volatile computerstorage media. For example, the memory 204 may include a RAM, includingdynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or staticRAM (“SRAM”). In some embodiments, the memory 204 includes non-volatilecomputer storage media. For example, the memory 204 may include a harddisk drive, a flash memory, or any other suitable non-volatile computerstorage device. In some embodiments, the memory 204 includes bothvolatile and non-volatile computer storage media. In some embodiments,the memory 204 also stores program code and related data, such as anoperating system or other controller algorithms operating on the remoteunit 102.

The input device 206, in one embodiment, may include any known computerinput device including a touch panel, a button, a keyboard, a stylus, amicrophone, or the like. In some embodiments, the input device 206 maybe integrated with the display 208, for example, as a touchscreen orsimilar touch-sensitive display. In some embodiments, the input device206 includes a touchscreen such that text may be input using a virtualkeyboard displayed on the touchscreen and/or by handwriting on thetouchscreen. In some embodiments, the input device 206 includes two ormore different devices, such as a keyboard and a touch panel.

The display 208, in one embodiment, may include any known electronicallycontrollable display or display device. The display 208 may be designedto output visual, audible, and/or haptic signals. In some embodiments,the display 208 includes an electronic display capable of outputtingvisual data to a user. For example, the display 208 may include, but isnot limited to, an LCD display, an LED display, an OLED display, aprojector, or similar display device capable of outputting images, text,or the like to a user. As another, non-limiting, example, the display208 may include a wearable display such as a smart watch, smart glasses,a heads-up display, or the like. Further, the display 208 may be acomponent of a smart phone, a personal digital assistant, a television,a table computer, a notebook (laptop) computer, a personal computer, avehicle dashboard, or the like.

In certain embodiments, the display 208 includes one or more speakersfor producing sound. For example, the display 208 may produce an audiblealert or notification (e.g., a beep or chime). In some embodiments, thedisplay 208 includes one or more haptic devices for producingvibrations, motion, or other haptic feedback. In some embodiments, allor portions of the display 208 may be integrated with the input device206. For example, the input device 206 and display 208 may form atouchscreen or similar touch-sensitive display. In other embodiments,the display 208 may be located near the input device 206.

The transmitter 210 is used to provide UL communication signals to thenetwork unit 104 and the receiver 212 is used to receive DLcommunication signals from the network unit 104, as described herein. Insome embodiments, the transmitter 210: transmits, to a device,configuration information on a transmission resource, wherein theconfiguration information comprises: resource information for a datatransmission; a request for feedback; and a configuration messageindicating configuration of a feedback resource; and transmits the datatransmission after the monitoring for feedback on the feedback resource.

In various embodiments, the receiver 212 receives configurationinformation on a reception resource, wherein the configurationinformation comprises: resource information for a data transmission; arequest for feedback; and a configuration message indicatingconfiguration of a feedback resource. In some embodiments, thetransmitter 210, in response to the processor determining to transmitthe feedback on the feedback resource, transmits the feedback from theapparatus on the feedback resource. In various embodiments, the receiver212 receives the data transmission after the feedback resource.

In some embodiments, the receiver 212 receives a data transmission viasidelink transmission. In certain embodiments, the transmitter 210, inresponse to determining that the half duplex problem exists with thedata transmission, retransmits the data transmission.

Although only one transmitter 210 and one receiver 212 are illustrated,the remote unit 102 may have any suitable number of transmitters 210 andreceivers 212. The transmitter 210 and the receiver 212 may be anysuitable type of transmitters and receivers. In one embodiment, thetransmitter 210 and the receiver 212 may be part of a transceiver.

FIG. 3 depicts one embodiment of an apparatus 300 that may be used forusing a configured feedback resource for feedback. The apparatus 300includes one embodiment of the network unit 104. Furthermore, thenetwork unit 104 may include a processor 302, a memory 304, an inputdevice 306, a display 308, a transmitter 310, and a receiver 312. As maybe appreciated, the processor 302, the memory 304, the input device 306,the display 308, the transmitter 310, and the receiver 312 may besubstantially similar to the processor 202, the memory 204, the inputdevice 206, the display 208, the transmitter 210, and the receiver 212of the remote unit 102, respectively.

In some embodiments, the transmitter 310 may transmit configurationinformation. Although only one transmitter 310 and one receiver 312 areillustrated, the network unit 104 may have any suitable number oftransmitters 310 and receivers 312. The transmitter 310 and the receiver312 may be any suitable type of transmitters and receivers. In oneembodiment, the transmitter 310 and the receiver 312 may be part of atransceiver.

In certain embodiments, such as for distributed resource allocation,half duplex constraints may limit a time at which UEs can transmit toenable all UEs in a group to receive the transmission from the UE. Insome embodiments, two UEs may transmit using a same time and/orfrequency resource block or timeslot (e.g., with different frequencyresource) and the resources may be used for several transmissions via aSPS allocation before a reselection. In such embodiments, severaltransmissions of the two UEs may have a half duplex problem or resourcecollision (e.g., if they select the same resource).

FIG. 4 is a schematic block diagram illustrating one embodiment of asystem 400 including multiple UEs transmitting at the same time anddifferent frequencies. The system 400 includes a first UE 402, a secondUE 404, and a third UE 406. The first UE 402 and the second UE 404 maytransmit data at the same time 408, but on different frequencies 410.Moreover, the third UE 406 may receive both transmissions from the firstUE 402 and the second UE 404 because the transmissions are on differentfrequencies 410. As may be appreciated, if the UEs operate in a halfduplex mode, they may not be able to transmit and receive at the sametime. Accordingly, while the first UE 402 and the second UE 404 aretransmitting data simultaneously, they are not able to receive data(e.g., receive the data transmitted from the other transmitting UE).

In some embodiments, there may be two SL resource allocation modes: Mode1 in which a BS schedules SL resources to be used by a UE for SLtransmissions; and Mode 2 in which a UE determines (e.g., the BS doesnot schedule) SL transmission resources within SL resources configuredby a BS and/or network or preconfigured SL resources.

In certain embodiments, the definition of SL resource allocation Mode 2covers: a) UE autonomously selects SL resource for transmission; b) UEassists SL resource selection for other UEs, a functionality which canbe part of a), c), and/or d); c) UE is configured with NR configuredgrant (Type-1 like) for SL transmission; and d) UE schedules SLtransmissions of other UEs.

In various embodiments, resource allocation Mode 2 supports reservationof SL resources at least for blind retransmission. In one embodiment,sensing and resource selection (or reselection) related procedures maybe supported for resource allocation Mode 2.

In some embodiments, a sensing procedure considered may be defined asdecoding SCI from other UEs and/or SL measurements. Decoding SCI mayprovide information on SL resources indicated by a UE transmitting theSCI. The sensing procedure may use a L1 SL RSRP measurement based on SLDMRS if a corresponding SCI is decoded.

In certain embodiments, a resource selection (or reselection) procedureconsidered may use the results of a sensing procedure to determineresources for SL transmission.

In one embodiment, in Mode 2(a), for SL sensing and resource selectionprocedures, in the context of a semi-persistent scheme in whichresources are selected for multiple transmissions of different TBs and adynamic scheme in which resources are selected for each TB transmission,the following techniques may be used to identify occupied SL resources:decoding of SL control channel transmissions; SL measurements; and/ordetection of SL transmissions. Moreover, the following aspects may beused for SL resource selection: how a UE selects resources for PSCCH andPSSCH transmission (and other SL physical channels and/or signals thatare defined); and/or what information is used by the UE for a resourceselection procedure.

In some embodiments, for out-of-coverage operation, Mode 2(c) may assumea configuration (or pre-configuration) of single or multiple SLtransmission patterns defined on each SL resource pool. In certainembodiments, for in-coverage operation, Mode 2(c) may assume that a gNBconfiguration indicates single or multiple SL transmission patternsdefined on each SL resource pool. In various embodiments, if there is asingle pattern configured for a transmitting UE, there may be no sensingprocedure executed by the UE if multiple patterns are configured andthere may be a possibility of a sensing procedure. As used herein, a“pattern” may be defined by a size and/or position of resources in timeand/or frequency, and by a number of resources.

In various embodiments, for Mode 2(d), in the context of group-based SLcommunication, a UE-A may inform its serving gNB about members UE-B,UE-C, and so on of a group, and the gNB may provide individual resourcepool configurations and/or individual resource configurations to eachgroup member through UE-A. In such embodiments, UE-A cannot modify theconfigurations, and there is no direct connection required between anymember UE and the gNB. Moreover, in such embodiments, higher-layersignaling may be the only signaling used to provide the configurationsand such functionality may be up to UE capabilities.

In certain embodiments, in the context of Mode-2(d), NR V2X may supportthe following functionality: a UE informs a gNB about group members andthe gNB provides individual resource pool configuration and/orindividual resource configuration through the same UE to each groupmember UE within the same group. This may not require a connectionbetween a member UE and the gNB. The UE may not modify the configurationprovided by gNB, higher layer signaling may be used to provide theconfiguration, and no physical layer signaling may be used; FFS if oneor both of the following options are supported—resource poolconfigurations and/or resource configuration; FFS if functionality isdefined as a part of Mode-2 if applicable for this feature; and/orfunctionality up to UE capabilities.

In certain embodiments, a UE may determine a set of resources to bereported to higher layers for PSSCH transmission if requested by higherlayers in subframe n for a carrier according to the following steps: 1)an interval between n+T1 and n+T2 may be a selection window. In thiswindow, CSRs may be selected after filtering out unusable resources.First, a UE marks those subframe resources as unavailable if the UE hasbeen transmitting in those subframes because the subframes at which a UEhas transmitted its packet may not be sensed by itself due tohalf-duplex transmission. Secondly, the UE excludes resources that areprobably used by other UEs, whether a resource was used or not may bedetermined by decoding PSCCH following steps: based on a resourcereservation and priority field in an SCI format 1; and/or based on ameasured S-RSRP higher than the configured threshold. After excludingresources based on above factors, the remaining resources are called aset SA; and 2) if single-subframe resources in SA are less than 20% ofthe entire selection window, then more candidate resources should beidentified. For this, we raise the RSRP threshold by 3 dB, and repeatthe above resource exclusion process. If SA becomes larger than 20%,then we choose those with the smallest RSSI values, which we call SB andreport SB to the MAC, where it randomly selects one of them for thetransmission. UE selection of T2 value for candidate resource selectionmay fulfill a latency requirement.

In various embodiments, one embodiment of content of SCI format 1 usedto schedule PSSCH is shown in Table 1.

TABLE 1 Priority 3 bits Resource reservation 4 bits Frequency resourcelocation ┌log₂(N_(subchannel) ^(SL) (N_(subchannel) ^(SL) + 1)/2┐ ofinitial transmission and retransmission Time gap between initial 4 bitstransmission and retransmission Modulation and coding scheme 5 bitsRetransmission index 1 bit Transmission format 1 bit

It should be noted that as used herein, eNB and/or gNB may be used for abase station but may also be replaceable by any other radio access node(e.g., BS, eNB, gNB, AP, NR, etc). Furthermore, methods described hereinmay be described mainly in the context of 5G NR, but may be applicableto other mobile communication systems supporting serving cells and/orcarriers configured for sidelink communication, such as for systems thatcommunicate over PC5 interface.

FIG. 5 is a schematic block diagram illustrating one embodiment of asystem 500 including multiple UEs transmitting at the same time in thesame group. The system 500 includes a first UE 502, a second UE 504, athird UE 506, a fourth UE 508, and a fifth UE 510 all within a group512.

Specifically, FIG. 5 illustrates one embodiment of group communicationwith an NR mode 2 based distributed resource allocation scheme in whichthe first UE 502 and the second UE 504 transmit using the same time slot(with different frequency resources) and cannot hear each other'stransmission and the third UE 506 is a SUE that assists group memberwith resource selection. The selection of SUE may be configured by a BSor a V2X application, and the UE ID of the SUE may be known to the groupmembers.

In a first embodiment, a reliability issue may arise due to a potentialhalf duplex constraint in a groupcast transmission and may besuccessfully mitigated with the aid of an SUE that periodically monitorsSCI transmissions from group member UEs and provides feedback if thereis any potential half duplex problem and/or resource collision.

FIG. 6 is a schematic block diagram illustrating one embodiment of aframe structure 600 that may be used to implement the first embodiment.The frame structure 600 illustrated with the time domain extendinghorizontally includes an SCI TX 602 (e.g., one or more time domainsymbols in which configuration information is transmitted, one or moreOFDM symbols) transmitted from a TX UE, a gap 604 (e.g., having a gaptime period in which there are no UEs transmitting, a set to time domainsymbols, a set of OFDM symbols), an SCI RX 606 (e.g., one or more timedomain symbol in which feedback is received, one or more OFDM symbols)received by the TX UE, and SL data 608 (e.g., a data transmissiontransmitted from the TX UE).

FIG. 7 is a schematic block diagram illustrating another embodiment of aframe structure 700 that may be used to implement the first embodiment.The frame structure 700 illustrated with the time domain extendinghorizontally includes an SCI TX 702 (e.g., one or more time domainsymbols in which configuration information is transmitted, one or moreOFDM symbols) transmitted from a TX UE, an SCI RX 704 (e.g., one or moretime domain symbol in which feedback is received, one or more OFDMsymbols) received by the TX UE, and SL data 706 (e.g., a datatransmission transmitted from the TX UE).

FIG. 8 is a schematic block diagram illustrating a further embodiment ofa frame structure 800 that may be used to implement the firstembodiment. The frame structure 800 illustrated with the time domainextending horizontally includes an SCI TX 802 (e.g., one or more timedomain symbols in which configuration information is transmitted, one ormore OFDM symbols) transmitted from a TX UE, a gap 804 (e.g., having agap time period in which there are no UEs transmitting, a set to timedomain symbols, a set of OFDM symbols), blank symbols 806 (e.g., blanksymb., one or more time domain symbol in which feedback is received, oneor more OFDM symbols) configured as symbols in which no transmissionsoccur from the TX UE, and SL data 808 (e.g., a data transmissiontransmitted from the TX UE).

FIG. 9 is a schematic block diagram illustrating yet another embodimentof a frame structure 900 that may be used to implement the firstembodiment. The frame structure 900 illustrated with the time domainextending horizontally includes an SCI TX 902 (e.g., one or more timedomain symbols in which configuration information is transmitted, one ormore OFDM symbols) transmitted from a TX UE, blank symbols 904 (e.g.,blank symb., one or more time domain symbol in which feedback isreceived, one or more OFDM symbols) configured as symbols in which notransmissions occur from the TX UE, and SL data 906 (e.g., a datatransmission transmitted from the TX UE).

As illustrated in FIGS. 6 and 7, TX UEs may transmit SCI in a beginningpart of the OFDM symbols (e.g., SCI TX) to group member UEs. The SCItransmission may contain resource information for a data transmission, acorresponding destination group identifier, a destination nodeidentifier, an indication for requesting feedback from an SUE, a slotformat indicator indicating a time domain symbol for feedback, and/or afeedback resource configuration.

In the subsequent OFDM symbols configured as blank symbols as shown inFIGS. 8 and 9 or labeled as SCI RX in FIGS. 6 and 7, the TX UE switchesto an RX mode before it transmits SL data. During a time duration of theblank symbols or the SCI RX, the TX UE checks for feedback from an SUEthat may indicate whether there is a half duplex problem. The blanksymbols are symbols in which TX UEs in a group do not make anytransmissions, but instead wait for reception of feedback from an SUE.

Thus, during the blank symbols, TX UEs do not transmit anything, TX UEsare switched to an RX mode, and only the SUE is enabled to transmitfeedback during this period. If there is a switching time or gaprequired then a flexible symbol (or symbols) may be inserted as a gap(e.g., the gap 604, the gap 804) before the blank symbols.

In some embodiments, TX UEs, if configured for half duplex detection,may select transmission resources from transmit resource pools. Theselection may be based on the reliability and/or latency requirement ofa groupcast packet transmission.

In certain embodiments, TX UEs may indicate configuration informationfor a feedback transmission that will be transmitted by an SUE. Theindication of the configuration information may be made dynamically inSCI, semi-statically in PC5 RRC, and/or by a gNB via RRC. One embodimentof configuration information is shown in Table 2. In variousembodiments, the configuration information includes: a flag to indicatea request for half duplex detection, a time domain symbol fortransmission of the feedback message by the SUE, a feedback timing, afeedback resource, an offset for the transmission of the feedbackmessage by the SUE, a resource option to be used by the SUE (e.g., acommon feedback resource, a dedicated feedback resource), a number ofblank symbols, and/or a number of OFDM symbols that create a switchinggap.

TABLE 2 Configuration Message Request for half duplex detection 1 bitFeedback timing and resource Xx bits Common feedback or dedicatedfeedback Xx bits Blank symbol(s) Xx bits Switching gap Xx bits

In various embodiments, TX UEs receive feedback (e.g., a feedbackindicator, a feedback message) and/or additional scheduling assistanceinformation from an SUE as shown in Table 3 in response to transmittingSCI. In such embodiments, the TX UEs may transmit based on thescheduling assistance information provided in the feedback message bythe SUE that may be based on a random back off timer. Table 3 shows oneembodiment of a feedback message that include a half duplex detectionindicator, and instructions for a TX UE with an identified source ID totransmit on a particular time slot or using an indicated offset. As maybe appreciated, the feedback message may include information for two ormore TX UEs that desire to transmit information at the during the sametime resources in order to assign the TX UEs different time resources sothat their transmissions do not occur at the same time.

TABLE 3 Feedback Message Half duplex detection 1 bit Source ID of TX UEXX bits Transmit time slot or offset XX bits Source ID of TX UE XX bitsTransmit time slot or offset XX bits

In some embodiments, if a TX UE transmits a message requesting feedbackfrom an SUE corresponding to half duplex detection and the TX UE doesnot detect a feedback message that includes the feedback during aconfigured time period, the TX UE may based on its own remaining packetdelay budget and/or priority determine to transmit the SL data in thesame time slot that it originally planned to or transmit the SL data ina different time slot based on a random back off timer.

In certain embodiments, if a TX UE transmits a message requestingfeedback from an SUE corresponding to half duplex detection and the TXUE receives on a common feedback resource, then, if the common feedbackresource indicates detection of a half duplex problem, the TX UE maytransmit SL data after a random back off timer.

In various embodiments, one RX UE may be configured as an SUE. In suchembodiments, the SUE may monitor SCI transmission from multiple TX UEsin a group, the SUE may periodically monitor, receive, and/or decode SCItransmitted from group member UEs in a configured resources as part of asensing procedure, the SUE may transmit feedback in configured blanksymbols to the TX UEs about a half duplex problem detection and/orresource collision. In some embodiments, if an SUE receives one or moreSCI transmission from group member UEs in the same or different OFDMsymbols of a time slot, the SUE may check one or more destination groupidentifiers and/or a resource selected for SL data transmission by groupmember UEs from their SCI.

In certain embodiments, if a destination group identifier indicated bygroup member TX UEs is identical and/or a resource selected by the groupmember TX UEs occupies the same time slot, then there is a potentialhalf duplex problem and an SUE may provide feedback with a correspondingindication to the TX UEs.

In various embodiments, if a destination group identifier indicated bygroup member TX UEs is not identical and/or a resource selected by thegroup member TX UEs do not occupy the same time slot, then there is nohalf duplex problem and an SUE may provide feedback to the TX UEs thatindicates that there is no half duplex problem.

In some embodiments, if a destination group identifier indicated bygroup member TX UEs is not identical and/or a resource selected by thegroup member TX UEs occupies the same time slot, then there is apotential half duplex problem and an SUE may (or may not) providefeedback with a corresponding indication to the TX UEs.

In certain embodiments, an SUE, based on a received feedbackconfiguration from TX UEs, may select a resource based on acorresponding feedback option and may transmit feedback in a commonfeedback resource and/or a dedicated feedback resource to TX UEs basedon a number of TX UEs transmitting in a time slot. The number of TX UEstransmitting in a time slot may be determined based on SCI reception.

In various embodiments, an SUE may be configured to transmit feedbackonly if there is a half duplex problem detected and may provide nofeedback transmission if there is no half duplex problem detected.

In some embodiments, a feedback transmission (e.g., feedback message)transmitted from an SUE may be carried by a PSCCH in the SCI RX shown inFIGS. 6 and 7 or in the blank symbols shown in FIGS. 8 and 9. Table 3shows one embodiment of information that may be included in a feedbackmessage. For example, the feedback message may include: an indicatorbased on a flag or a bit that provides feedback information (e.g., ‘0’for no half duplex problem and ‘1’ for half duplex problem detection);and or source IDs of TX UEs for each TX UE or group IDs if a commonfeedback resource is used.

In certain embodiments, an SUE may provide additional assistanceinformation such as different time slots or OFDM symbols configurationto TX UEs to facilitate avoiding a problem in the same or subsequenttransmissions. In one embodiment, based on a priority indicated by TXUEs in SCI, an SUE that detects a half duplex problem may providefeedback to one TX UE to transmit in an originally planned time slotand/or symbols and may provide feedback to another TX UE to transmit ina different non-overlapping time slot and/or symbols.

In various embodiments, a BS may configure separate resource pools withblank symbols as described in relation to FIGS. 8 and 9. In suchembodiments, the BS may broadcast the configuration of the resourcepools as part of a system information block and/or the configuration maybe configured (or preconfigured) for NR Mode 2 operations. In suchembodiments, the configuration of the resource pools by the gNB or theotherwise provided configuration (or preconfiguration) may contain anindication of one or more time domain symbols for: SCI transmission,blank symbols, SL data transmission, and/or sidelink HARQ feedback.

In some embodiments, configuration of a sidelink frame structureindicating blank symbols may be indicated by: a SL-SFI by a gNB in DCI(e.g., format 5A), a system information block for sidelink, an RRCconfiguration for sidelink, and/or other sidelink UEs either in SCI orPC5 RRC. As may be appreciated, configured blank symbols may be for agroup of UEs in a cell or for certain geographical areas. In certainembodiments, flexible symbols may be explicitly configured as blanksymbols. As may be appreciated, a flexible symbol may be an OFDM symbolin a slot that may be configured as DL, UL, SL, and/or a blank symbol.In various embodiments, a configuration that enables half duplexdetection may be configured by a BS.

While FIGS. 6, 7, 8, and 9 illustrate certain examples of framesstructures used to implement the first embodiment, other framestructures may also be used. For example, FIG. 10A is a schematic blockdiagram illustrating an additional embodiment of a frame structure 1000that may be used to implement the first embodiment.

The frame structure 1000 is illustrated with the time domain extendinghorizontally and includes a first slot (N) 1002 and a second slot (N+1)1004. The first slot (N) 1002 includes an SCI TX (N) 1006 (e.g., one ormore time domain symbols in which configuration information istransmitted in slot N, one or more OFDM symbols transmitted in slot N)transmitted from a TX UE, SL Data (N−1) 1008 (e.g., a data transmissiontransmitted from the TX UE that corresponds to configuration informationtransmitted in slot N−1—the slot that would precede the first slot (N)1002), and PSFCH (N) 1010 (e.g., one or more time domain symbol in whichfeedback is received that corresponds to SCI TX (N) 1006, one or moreOFDM symbols in which feedback is received that corresponds to SCI TX(N) 1006). The second slot (N+1) 1004 includes an SCI TX (N+1) 1012(e.g., one or more time domain symbols in which configurationinformation is transmitted in slot N+1, one or more OFDM symbolstransmitted in slot N+1) transmitted from a TX UE, SL Data (N) 1014(e.g., a data transmission transmitted from the TX UE that correspondsto configuration information transmitted in the first slot (N) 1002),and PSFCH (N+1) 1016 (e.g., one or more time domain symbol in whichfeedback is received that corresponds to SCI TX (N+1) 1012, one or moreOFDM symbols in which feedback is received that corresponds to SCI TX(N+1) 1012). As may be appreciated, based on the feedback provided inPSFCH (N) 1010, the TX UE may determine whether to transmit the SL data(N) 1014 in the second slot (N+1) 1004. In another method, the feedbackmay be transmitted for the SL data (N) with PSFCH in the same time slotas illustrated in FIG. 10B.

FIG. 10B is a schematic block diagram illustrating another embodiment ofa frame structure 1020 that may be used to implement the firstembodiment.

The frame structure 1020 is illustrated with the time domain extendinghorizontally and includes a first slot (N) 1022 and a second slot (N+1)1024. The first slot (N) 1022 includes an SCI TX (N) 1026 (e.g., one ormore time domain symbols in which configuration information istransmitted in the first slot (N) 1022, one or more OFDM symbolstransmitted in the first slot (N) 1022) transmitted from a TX UE, SLData (N) 1028 (e.g., a data transmission transmitted from the TX UE thatcorresponds to configuration information transmitted in the first slot(N) 1022), and PSFCH (N) 1030 (e.g., one or more time domain symbol inwhich feedback is received that corresponds to SCI TX (N) 1026, one ormore OFDM symbols in which feedback is received that corresponds to SCITX (N) 1026). The second slot (N+1) 1024 includes an SCI TX (N+1) 1032(e.g., one or more time domain symbols in which configurationinformation is transmitted in the second slot (N+1) 1024, one or moreOFDM symbols transmitted in the second slot (N+1) 1024) transmitted froma TX UE, SL Data (N+1) 1034 (e.g., a data transmission transmitted fromthe TX UE that corresponds to configuration information transmitted inthe second slot (N+1) 1024), and PSFCH (N+1) 1036 (e.g., one or moretime domain symbol in which feedback is received that corresponds to SCITX (N+1) 1032, one or more OFDM symbols in which feedback is receivedthat corresponds to SCI TX (N+1) 1032).

FIG. 11 is a schematic block diagram illustrating one embodiment ofcommunications 1100 corresponding to group transmissions. Thecommunications 1100 may include communications between a gNB 1102, anSUE 1104, and group UEs 1106. As may be appreciated, descriptions ofcommunications contained herein may refer to one or more messagestransmitted between devices.

In one embodiment, in a first communication 1108 transmitted from thegNB 1102 to the SUE 1104, the gNB 1102 may transmit a configurationmessage to the SUE 1104 to indicate a configuration for SCI and/or afeedback message. In some embodiments, in a second communication 1110transmitted between the SUE 1104 and the group UEs 1106, theconfiguration message may be provided from the SUE 1104 to the group UEs1106. In certain embodiments, in a third communication 1112 transmittedbetween the group UEs 1106 and the SUE 1104, one or more of the groupUEs 1106 may transmit SCI for groupcast data. In various embodiments, ina fourth communication 1114 transmitted from the SUE 1104 to the groupUEs 1106, the SUE 1104 may provide a feedback message corresponding tothe SCI to the group UEs 1106 (e.g., to the TX UEs). In someembodiments, in a fifth communication 1116 transmitted between the groupUEs 1106 and the SUE 1104, groupcast data may be transmitted by one ormore TX UEs of the group UEs 1106.

In a second embodiment, a feedback message may be sent by any UE in a UEgroup (e.g., not just an SUE). In some cases, a gNB may configure athreshold based on an L1 sidelink RSRP or a configured (orpreconfigured) threshold, and a feedback transmission may be transmittedby UEs that are above the configured threshold.

The feedback message may be sent using dedicated L1 signaling toindicate half duplex detection to TX UEs. In one embodiment, the L1signaling may use PSFCH or PSCCH (e.g., SCI) transmission resources. Incertain embodiments, feedback resource configuration may be transmittedby a gNB and/or an SUE. In various embodiments, if PSFCH is used, acommon or dedicated feedback configuration may be used.

In some embodiments, if a group member UE detects a half duplex problemas one or more TX UEs are transmitting in the same time slot, even if SLdata (e.g., PSSCH) is successfully decoded, the group member UEs maytransmit one or more NACKs in a common or dedicated feedback resource toimplicitly indicate a potential half duplex problem and the one or moreTX UEs may transmit (or retransmit) a corresponding transport blockbased on the feedback.

In a third embodiment, an RX UE configured as a SUE may: monitor SCItransmissions from multiple TX UEs from a group, receive and/or decodeSCI transmitted from group member UEs in configured resources as part ofa sensing procedure, and transmit (or retransmit) a group packet to theTX UEs if a half duplex problem is detected and/or a resource collisionis detected. Thus, the SUE may directly retransmit the simultaneouslytransmitted data so that TX UEs do not have to schedule retransmissionof the data as in other embodiments. For the transmission (orretransmission), the SUE may use a source ID of the TX UEs as found inL1 and/or L2 signaling.

In certain embodiments, a TX UE may indicate in SCI about a request forhalf duplex detection and transmission (or retransmission) by an SUE.The TX UEs may reserve a time slot and/or resource for transmission (orretransmission) by the SUE and may indicate the reservation in SCI.

In a fourth embodiment, a sensing method for selecting candidateresources may be improved based on TX UEs receiving feedback messagesfor half duplex detection. For example, in a resource exclusion process,if a requested or configured feedback message successfully indicates toone or more TX UEs that there is no half duplex problem, then thecandidate resources for that time slot (e.g., the time slot in whichfeedback is requested) is included in the candidate resource selectionprocess.

In some embodiments, if a feedback message indicates a half duplexproblem, then there may be a potential transmission from other memberUEs in the same time slot, however candidate resource selection processmay also depend on a potential resource collision detection with thesame or overlapping frequency resources. A determination of whether theresources selected by two or more TX UEs collide (or not) may be basedon assistance signaling either from group member UEs or an SUE using L1signaling, such as PSCCH or PSFCH.

FIG. 12 is a flow chart diagram illustrating one embodiment of a method1200 for using a configured feedback resource for feedback. In someembodiments, the method 1200 is performed by an apparatus, such as theremote unit 102. In certain embodiments, the method 1200 may beperformed by a processor executing program code, for example, amicrocontroller, a microprocessor, a CPU, a GPU, an auxiliary processingunit, a FPGA, or the like.

The method 1200 may include transmitting 1202, to a device,configuration information on a transmission resource, wherein theconfiguration information comprises: resource information for a datatransmission; a request for feedback; and a configuration messageindicating configuration of a feedback resource. In certain embodiments,the method 1200 includes monitoring 1204 for feedback from the device onthe feedback resource. In various embodiments, the method 1200 includestransmitting 1206 the data transmission after the monitoring forfeedback on the feedback resource.

In certain embodiments, a gap time period in terms of time domainsymbols occurs between a time domain symbol in which the configurationinformation is transmitted and a time domain symbol in which thefeedback is received. In some embodiments, the feedback resource isreceived in a time domain symbol directly after a time domain symbol inwhich the configuration information is transmitted. In variousembodiments, the feedback indicates whether there is a half duplexproblem detection, a resource collision, or a combination thereof.

In one embodiment, the configuration of the feedback resource comprisesinformation indicating a time domain symbol for the feedback. In certainembodiments, the feedback resource comprises orthogonal frequencydivision multiplexed symbols configured as blank symbols. In someembodiments, no transmissions are made on the blank symbol except thefeedback transmission made by the device.

In various embodiments, the method 1200 further comprises selecting thetransmission resource and the feedback resource from a resource pool. Inone embodiment, transmitting the configuration information comprisestransmitting the configuration information within sidelink controlinformation, transmitting the configuration information using a radioresource control message, receiving the configuration message as part ofdownlink control information, receiving the configuration message aspart of radio resource control information, or some combination thereof.In certain embodiments, the feedback resource comprises a commonfeedback resource or a dedicated feedback resource.

In some embodiments, the configuration information comprises anindication of a half duplex problem detection. In various embodiments,transmitting the data transmission comprises transmitting the datatransmission based on the feedback corresponding to a half duplexproblem detection. In one embodiment, transmitting the data transmissionbased on the feedback corresponding to the half duplex problem detectioncomprises transmitting the data transmission based on an indicated timeslot in a feedback message or based on a random back off timer.

In certain embodiments, the method 1200 further comprises, in responseto monitoring for the feedback on the feedback resource resulting in notdetecting the feedback, transmitting the data transmission based on arandom back off timer, a remaining packet delay budget, a priority, or acombination thereof. In some embodiments, transmitting the datatransmission based on the random back off timer, the remaining packetdelay budget, the priority, or the combination thereof comprisestransmitting the data transmission in a prior determined time slot, ortransmitting the data transmission in a time slot determined based on arandom back off timer. In various embodiments, the device comprises ascheduling user equipment, and the scheduling user equipment belongs toa destination group.

In one embodiment, the device comprises one or more non-scheduling userequipments. In certain embodiments, the data transmission occurs in aslot after the transmission resource and the feedback resource. In someembodiments, the feedback resource is used to carry a negativeacknowledgment that indicates detection of a potential half duplexproblem.

In various embodiments, the feedback indicates that there is not a halfduplex problem detected. In one embodiment, the method 1200 furthercomprises transmitting a second data transmission on a second feedbackresource.

FIG. 13 is a flow chart diagram illustrating another embodiment of amethod 1300 for using a configured feedback resource for feedback. Insome embodiments, the method 1300 is performed by an apparatus, such asthe remote unit 102. In certain embodiments, the method 1300 may beperformed by a processor executing program code, for example, amicrocontroller, a microprocessor, a CPU, a GPU, an auxiliary processingunit, a FPGA, or the like.

The method 1300 may include receiving 1302, at a device, configurationinformation on a reception resource, wherein the configurationinformation comprises: resource information for a data transmission; arequest for feedback; and a configuration message indicatingconfiguration of a feedback resource. In certain embodiments, the method1300 includes determining 1304 whether to transmit feedback on thefeedback resource. In some embodiments, the method 1300 includes, inresponse to determining to transmit the feedback on the feedbackresource, transmitting 1306 the feedback from the device on the feedbackresource. In various embodiments, the method 1300 includes receiving1308 the data transmission after the feedback resource.

In certain embodiments, a gap time period in terms of time domainsymbols occurs between a time domain symbol in which the configurationinformation is transmitted and a time domain symbol in which thefeedback is received. In some embodiments, the feedback resource isreceived in a time domain symbol directly after a time domain symbol inwhich the configuration information is transmitted. In variousembodiments, the feedback indicates whether there is a half duplexproblem detection, a resource collision, or a combination thereof.

In one embodiment, the configuration of the feedback resource comprisesinformation indicating a time domain symbol for the feedback. In certainembodiments, the feedback resource comprises orthogonal frequencydivision multiplexed symbols configured as blank symbols. In someembodiments, no transmissions are made on the blank symbol except thefeedback transmission made by the device.

In various embodiments, the transmission resource and the feedbackresource are selected from a resource pool. In one embodiment, receivingthe configuration information comprises receiving the configurationinformation within sidelink control information, receiving theconfiguration information using a radio resource control message,receiving the configuration message as part of downlink controlinformation, receiving the configuration message as part of radioresource control information, or some combination thereof. In certainembodiments, the feedback resource comprises a common feedback resourceor a dedicated feedback resource.

In some embodiments, the configuration information comprises anindication of a half duplex problem detection. In various embodiments,receiving the data transmission comprises receiving the datatransmission based on the feedback corresponding to a half duplexproblem detection. In one embodiment, receiving the data transmissionbased on the feedback corresponding to the half duplex problem detectioncomprises receiving the data transmission based on an indicated timeslot in a feedback message or based on a random back off timer.

In certain embodiments, the method 1300 further comprises, in responseto determining not to transmit the feedback on the feedback resource,receiving the data transmission based on a random back off timer, aremaining packet delay budget, a priority, or a combination thereof. Insome embodiments, receiving the data transmission based on the randomback off timer, the remaining packet delay budget, the priority, or thecombination thereof comprises receiving the data transmission in a priordetermined time slot, or receiving the data transmission in a time slotdetermined based on a random back off timer. In various embodiments, thedevice comprises a scheduling user equipment, and the scheduling userequipment belongs to a destination group.

In one embodiment, the device comprises one or more non-scheduling userequipments. In certain embodiments, the data transmission occurs in aslot after the transmission resource and the feedback resource. In someembodiments, the feedback resource is used to carry a negativeacknowledgment that indicates detection of a potential half duplexproblem.

FIG. 14 is a flow chart diagram illustrating one embodiment of a method1400 for retransmitting data. In some embodiments, the method 1400 isperformed by an apparatus, such as the remote unit 102. In certainembodiments, the method 1400 may be performed by a processor executingprogram code, for example, a microcontroller, a microprocessor, a CPU, aGPU, an auxiliary processing unit, a FPGA, or the like.

The method 1400 may include receiving 1402, at a device, a datatransmission via sidelink transmission. In certain embodiments, themethod 1400 includes determining 1404 whether a half duplex problemexists with the data transmission. In some embodiments, the method 1400includes, in response to determining that the half duplex problem existswith the data transmission, retransmitting 1406 the data transmission.

In certain embodiments, the device comprises a scheduling userequipment, and the scheduling user equipment belongs to a destinationgroup. In some embodiments, the device comprises a non-scheduling userequipment.

In one embodiment, a method comprises: transmitting, to a device,configuration information on a transmission resource, wherein theconfiguration information comprises: resource information for a datatransmission; a request for feedback; and a configuration messageindicating configuration of a feedback resource; monitoring for feedbackfrom the device on the feedback resource; and transmitting the datatransmission after the monitoring for feedback on the feedback resource.

In certain embodiments, a gap time period in terms of time domainsymbols occurs between a time domain symbol in which the configurationinformation is transmitted and a time domain symbol in which thefeedback is received.

In some embodiments, the feedback resource is received in a time domainsymbol directly after a time domain symbol in which the configurationinformation is transmitted.

In various embodiments, the feedback indicates whether there is a halfduplex problem detection, a resource collision, or a combinationthereof.

In one embodiment, the configuration of the feedback resource comprisesinformation indicating a time domain symbol for the feedback.

In certain embodiments, the feedback resource comprises orthogonalfrequency division multiplexed symbols configured as blank symbols.

In some embodiments, no transmissions are made on the blank symbolexcept the feedback transmission made by the device.

In various embodiments, the method further comprises selecting thetransmission resource and the feedback resource from a resource pool.

In one embodiment, transmitting the configuration information comprisestransmitting the configuration information within sidelink controlinformation, transmitting the configuration information using a radioresource control message, receiving the configuration message as part ofdownlink control information, receiving the configuration message aspart of radio resource control information, or some combination thereof.

In certain embodiments, the feedback resource comprises a commonfeedback resource or a dedicated feedback resource.

In some embodiments, the configuration information comprises anindication of a half duplex problem detection.

In various embodiments, transmitting the data transmission comprisestransmitting the data transmission based on the feedback correspondingto a half duplex problem detection.

In one embodiment, transmitting the data transmission based on thefeedback corresponding to the half duplex problem detection comprisestransmitting the data transmission based on an indicated time slot in afeedback message or based on a random back off timer.

In certain embodiments, the method further comprises, in response tomonitoring for the feedback on the feedback resource resulting in notdetecting the feedback, transmitting the data transmission based on arandom back off timer, a remaining packet delay budget, a priority, or acombination thereof.

In some embodiments, transmitting the data transmission based on therandom back off timer, the remaining packet delay budget, the priority,or the combination thereof comprises transmitting the data transmissionin a prior determined time slot, or transmitting the data transmissionin a time slot determined based on a random back off timer.

In various embodiments, the device comprises a scheduling userequipment, and the scheduling user equipment belongs to a destinationgroup.

In one embodiment, the device comprises one or more non-scheduling userequipments.

In certain embodiments, the data transmission occurs in a slot after thetransmission resource and the feedback resource.

In some embodiments, the feedback resource is used to carry a negativeacknowledgment that indicates detection of a potential half duplexproblem.

In various embodiments, the feedback indicates that there is not a halfduplex problem detected.

In one embodiment, the method further comprises transmitting a seconddata transmission on a second feedback resource.

In one embodiment, an apparatus comprises: a transmitter that transmits,to a device, configuration information on a transmission resource,wherein the configuration information comprises: resource informationfor a data transmission; a request for feedback; and a configurationmessage indicating configuration of a feedback resource; and a processorthat monitors for feedback from the device on the feedback resource;wherein the transmitter transmits the data transmission after themonitoring for feedback on the feedback resource.

In certain embodiments, a gap time period in terms of time domainsymbols occurs between a time domain symbol in which the configurationinformation is transmitted and a time domain symbol in which thefeedback is received.

In some embodiments, the feedback resource is received in a time domainsymbol directly after a time domain symbol in which the configurationinformation is transmitted.

In various embodiments, the feedback indicates whether there is a halfduplex problem detection, a resource collision, or a combinationthereof.

In one embodiment, the configuration of the feedback resource comprisesinformation indicating a time domain symbol for the feedback.

In certain embodiments, the feedback resource comprises orthogonalfrequency division multiplexed symbols configured as blank symbols.

In some embodiments, no transmissions are made on the blank symbolexcept the feedback transmission made by the device.

In various embodiments, the processor selects the transmission resourceand the feedback resource from a resource pool.

In one embodiment, the apparatus further comprises a receiver, whereinthe transmitter transmitting the configuration information comprises thetransmitter transmitting the configuration information within sidelinkcontrol information, the transmitter transmitting the configurationinformation using a radio resource control message, the receiverreceiving the configuration message as part of downlink controlinformation, the receiver receiving the configuration message as part ofradio resource control information, or some combination thereof.

In certain embodiments, the feedback resource comprises a commonfeedback resource or a dedicated feedback resource.

In some embodiments, the configuration information comprises anindication of a half duplex problem detection.

In various embodiments, the transmitter transmitting the datatransmission comprises the transmitter transmitting the datatransmission based on the feedback corresponding to a half duplexproblem detection.

In one embodiment, the transmitter transmitting the data transmissionbased on the feedback corresponding to the half duplex problem detectioncomprises the transmitter transmitting the data transmission based on anindicated time slot in a feedback message or based on a random back offtimer.

In certain embodiments, in response to the processor monitoring for thefeedback on the feedback resource resulting in not detecting thefeedback, the transmitter transmits the data transmission based on arandom back off timer, a remaining packet delay budget, a priority, or acombination thereof.

In some embodiments, the transmitter transmitting the data transmissionbased on the random back off timer, the remaining packet delay budget,the priority, or the combination thereof comprises the transmittertransmitting the data transmission in a prior determined time slot, ortransmitting the data transmission in a time slot determined based on arandom back off timer.

In various embodiments, the device comprises a scheduling userequipment, and the scheduling user equipment belongs to a destinationgroup.

In one embodiment, the device comprises one or more non-scheduling userequipments.

In certain embodiments, the data transmission occurs in a slot after thetransmission resource and the feedback resource.

In some embodiments, the feedback resource is used to carry a negativeacknowledgment that indicates detection of a potential half duplexproblem.

In various embodiments, the feedback indicates that there is not a halfduplex problem detected.

In one embodiment, the transmitter transmits a second data transmissionon a second feedback resource.

In one embodiment, a method comprises: receiving, at a device,configuration information on a reception resource, wherein theconfiguration information comprises: resource information for a datatransmission; a request for feedback; and a configuration messageindicating configuration of a feedback resource; determining whether totransmit feedback on the feedback resource; in response to determiningto transmit the feedback on the feedback resource, transmitting thefeedback from the device on the feedback resource; and receiving thedata transmission after the feedback resource.

In certain embodiments, a gap time period in terms of time domainsymbols occurs between a time domain symbol in which the configurationinformation is transmitted and a time domain symbol in which thefeedback is received.

In some embodiments, the feedback resource is received in a time domainsymbol directly after a time domain symbol in which the configurationinformation is transmitted.

In various embodiments, the feedback indicates whether there is a halfduplex problem detection, a resource collision, or a combinationthereof.

In one embodiment, the configuration of the feedback resource comprisesinformation indicating a time domain symbol for the feedback.

In certain embodiments, the feedback resource comprises orthogonalfrequency division multiplexed symbols configured as blank symbols.

In some embodiments, no transmissions are made on the blank symbolexcept the feedback transmission made by the device.

In various embodiments, the transmission resource and the feedbackresource are selected from a resource pool.

In one embodiment, receiving the configuration information comprisesreceiving the configuration information within sidelink controlinformation, receiving the configuration information using a radioresource control message, receiving the configuration message as part ofdownlink control information, receiving the configuration message aspart of radio resource control information, or some combination thereof.

In certain embodiments, the feedback resource comprises a commonfeedback resource or a dedicated feedback resource.

In some embodiments, the configuration information comprises anindication of a half duplex problem detection.

In various embodiments, receiving the data transmission comprisesreceiving the data transmission based on the feedback corresponding to ahalf duplex problem detection.

In one embodiment, receiving the data transmission based on the feedbackcorresponding to the half duplex problem detection comprises receivingthe data transmission based on an indicated time slot in a feedbackmessage or based on a random back off timer.

In certain embodiments, the method further comprises, in response todetermining not to transmit the feedback on the feedback resource,receiving the data transmission based on a random back off timer, aremaining packet delay budget, a priority, or a combination thereof.

In some embodiments, receiving the data transmission based on the randomback off timer, the remaining packet delay budget, the priority, or thecombination thereof comprises receiving the data transmission in a priordetermined time slot, or receiving the data transmission in a time slotdetermined based on a random back off timer.

In various embodiments, the device comprises a scheduling userequipment, and the scheduling user equipment belongs to a destinationgroup.

In one embodiment, the device comprises one or more non-scheduling userequipments.

In certain embodiments, the data transmission occurs in a slot after thetransmission resource and the feedback resource.

In some embodiments, the feedback resource is used to carry a negativeacknowledgment that indicates detection of a potential half duplexproblem.

In one embodiment, an apparatus comprises: a receiver that receivesconfiguration information on a reception resource, wherein theconfiguration information comprises: resource information for a datatransmission; a request for feedback; and a configuration messageindicating configuration of a feedback resource; a processor thatdetermines whether to transmit feedback on the feedback resource; and atransmitter that, in response to the processor determining to transmitthe feedback on the feedback resource, transmits the feedback from theapparatus on the feedback resource; wherein the receiver receives thedata transmission after the feedback resource.

In certain embodiments, a gap time period in terms of time domainsymbols occurs between a time domain symbol in which the configurationinformation is transmitted and a time domain symbol in which thefeedback is received.

In some embodiments, the feedback resource is received in a time domainsymbol directly after a time domain symbol in which the configurationinformation is transmitted.

In various embodiments, the feedback indicates whether there is a halfduplex problem detection, a resource collision, or a combinationthereof.

In one embodiment, the configuration of the feedback resource comprisesinformation indicating a time domain symbol for the feedback.

In certain embodiments, the feedback resource comprises orthogonalfrequency division multiplexed symbols configured as blank symbols.

In some embodiments, no transmissions are made on the blank symbolexcept the feedback transmission made by the apparatus.

In various embodiments, the transmission resource and the feedbackresource are selected from a resource pool.

In one embodiment, the receiver receiving the configuration informationcomprises the receiver receiving the configuration information withinsidelink control information, the receiver receiving the configurationinformation using a radio resource control message, the receiverreceiving the configuration message as part of downlink controlinformation, the receiver receiving the configuration message as part ofradio resource control information, or some combination thereof.

In certain embodiments, the feedback resource comprises a commonfeedback resource or a dedicated feedback resource.

In some embodiments, the configuration information comprises anindication of a half duplex problem detection.

In various embodiments, the receiver receiving the data transmissioncomprises the receiver receiving the data transmission based on thefeedback corresponding to a half duplex problem detection.

In one embodiment, the receiver receiving the data transmission based onthe feedback corresponding to the half duplex problem detectioncomprises the receiver receiving the data transmission based on anindicated time slot in a feedback message or based on a random back offtimer.

In certain embodiments, in response to determining not to transmit thefeedback on the feedback resource, the receiver receives the datatransmission based on a random back off timer, a remaining packet delaybudget, a priority, or a combination thereof.

In some embodiments, the receiver receiving the data transmission basedon the random back off timer, the remaining packet delay budget, thepriority, or the combination thereof comprises the receiver receivingthe data transmission in a prior determined time slot, or receiving thedata transmission in a time slot determined based on a random back offtimer.

In various embodiments, the apparatus comprises a scheduling userequipment, and the scheduling user equipment belongs to a destinationgroup.

In one embodiment, the apparatus comprises one or more non-schedulinguser equipments.

In certain embodiments, the data transmission occurs in a slot after thetransmission resource and the feedback resource.

In some embodiments, the feedback resource is used to carry a negativeacknowledgment that indicates detection of a potential half duplexproblem.

In one embodiment, a method comprises: receiving, at a device, a datatransmission via sidelink transmission; determining whether a halfduplex problem exists with the data transmission; and in response todetermining that the half duplex problem exists with the datatransmission, retransmitting the data transmission.

In certain embodiments, the device comprises a scheduling userequipment, and the scheduling user equipment belongs to a destinationgroup.

In some embodiments, the device comprises a non-scheduling userequipment.

In one embodiment, an apparatus comprises: a receiver that receives adata transmission via sidelink transmission; a processor that determineswhether a half duplex problem exists with the data transmission; and atransmitter that, in response to determining that the half duplexproblem exists with the data transmission, retransmits the datatransmission.

In certain embodiments, the apparatus comprises a scheduling userequipment, and the scheduling user equipment belongs to a destinationgroup.

In some embodiments, the apparatus comprises a non-scheduling userequipment.

Embodiments may be practiced in other specific forms. The describedembodiments are to be considered in all respects only as illustrativeand not restrictive. The scope of the invention is, therefore, indicatedby the appended claims rather than by the foregoing description. Allchanges which come within the meaning and range of equivalency of theclaims are to be embraced within their scope.

1. A method comprising: transmitting, to a device, configuration information on a transmission resource, wherein the configuration information comprises: instructions to monitor a physical sidelink control channel in at least one resource pool; and a configuration message indicating configuration of a feedback resource; monitoring for feedback from the device on the feedback resource, wherein the feedback comprises feedback indicating whether there is detection of a half duplex problem, a resource collision, or a combination thereof in a resource indicated in the at least one resource pool ; determining whether to transmit a data transmission based on a result of monitoring for the feedback; and in response to determining to transmit the data transmission, transmitting the data transmission.
 2. The method of claim 1, wherein a gap time period in terms of time domain symbols occurs between a time domain symbol in which the configuration information is transmitted and a time domain symbol in which the feedback is received.
 3. The method of claim 1, wherein the feedback resource is received in a time domain symbol directly after a time domain symbol in which the configuration information is transmitted.
 4. (canceled)
 5. The method of claim 1, wherein the configuration of the feedback resource comprises information indicating a time domain symbol for the feedback.
 6. The method of claim 1, wherein the feedback resource comprises orthogonal frequency division multiplexed symbols configured as a physical sidelink feedback channel blank symbols.
 7. (canceled)
 8. (canceled)
 9. (canceled)
 10. The method of claim 1, wherein the feedback indicates that there is not a half duplex problem detected.
 11. An apparatus comprising: a transmitter that transmits, to a device, configuration information on a transmission resource, wherein the configuration information comprises: instructions to monitor a physical sidelink control channel in at least one resource pool; and a configuration message indicating configuration of a feedback resource; and a processor that: monitors for feedback from the device on the feedback resource, wherein the feedback comprises feedback indicating whether there is detection of a half duplex problem, a resource collision, or a combination thereof in a resource indicated in the at least one resource pool; and determines whether to transmit a data transmission based on a result of monitoring for the feedback; wherein, in response to determining to transmit the data transmission, the transmitter transmits the data transmission.
 12. The apparatus of claim 11, further comprising a receiver, wherein the transmitter transmitting the configuration information comprises the transmitter transmitting the configuration information within sidelink control information, the transmitter transmitting the configuration information using a radio resource control message, the receiver receiving the configuration message as part of downlink control information, the receiver receiving the configuration message as part of radio resource control information, or some combination thereof.
 13. The apparatus of claim 11, wherein the transmitter transmitting the data transmission comprises the transmitter transmitting the data transmission based on the feedback corresponding to the half duplex problem.
 14. The apparatus of claim 13, wherein the transmitter transmitting the data transmission based on the feedback corresponding to the half duplex problem comprises the transmitter transmitting the data transmission based on an indicated time slot in a feedback message or based on a random back off timer.
 15. The apparatus of claim 11, wherein, in response to the processor monitoring for the feedback on the feedback resource resulting in not detecting the feedback, the transmitter transmits the data transmission based on a random back off timer, a remaining packet delay budget, a priority, or a combination thereof.
 16. The apparatus of claim 15, wherein the transmitter transmitting the data transmission based on the random back off timer, the remaining packet delay budget, the priority, or the combination thereof comprises the transmitter transmitting the data transmission in a prior determined time slot, or transmitting the data transmission in a time slot determined based on the random back off timer.
 17. A method comprising: receiving, at a device, configuration information on a reception resource, wherein the configuration information comprises: instructions to monitor a physical sidelink control channel in at least one resource pool; and a configuration message indicating configuration of a feedback resource; decoding the physical sidelink control channel to determine a half duplex problem, a resource collision, or a combination thereof in the at least one resource pool; transmitting feedback from the device on the feedback resource in response to determining the half duplex problem, the resource collision, or the combination thereof in the at least one resource pool ; and receiving a data transmission after the feedback resource.
 18. (canceled)
 19. (canceled)
 20. (canceled)
 21. The method of claim 1, wherein the feedback comprises a negative acknowledgement in response to there being the half duplex problem, the resource collision, or the combination thereof even if sidelink data is successfully decoded.
 22. The apparatus of claim 11, wherein the feedback comprises a negative acknowledgement in response to there being the half duplex problem, the resource collision, or the combination thereof even if sidelink data is successfully decoded.
 23. The method of claim 17, wherein the feedback comprises a negative acknowledgement in response to there being the half duplex problem, the resource collision, or the combination thereof even if sidelink data is successfully decoded. 